This is the public Retail3000 API documentation. Any comments are welcome at developmentNO-SPAM@nedfox.nl.

Summary

Retail3000 is the engine behind several user interface applications, like RetailVista, RetailEverywhere and RetailVista POS. The key items that make Retail3000 unique is that it's not some kind of a few additions so extenal parties can communicate with our backoffice environment. Retail3000 is the only way to communicate with the database backend of our core RetailVista application. We use Retail3000 ourself to interface our several user interface applications with the database backend. So you can be assured that everything you see in our user interfaces can be build again and re-used in your own backend systems. In our opinion, the only way to be a real 'open' application.

Communication with the Retail3000 engine is done at this moment with webservice, also known as 'soap'. In this documentation you will find all our available webservice methods. We will also provide samples how to achive certain interfaces, but we do this based on requests. If you need any information how to achive some functionality, please don't hesiate to contact us and we'll publish some samples if not available yet.

Language

All samples in this documentation are based on Microsoft.Net C#. Although we would like, we can't provide support on other languages. Please be advised to use several forums on the public Internet to transform C# requests to langues like PHP etcetera.

Access

To be able to communicate with the Retail3000 API, NedFox will need to give access. By default, our API environment can't be reached from the outside world. On request, we will setup a test environment so a third party ISV can develop an integration with our systems. When that has been tested succesfully, our firewall environment will be adjusted to give a third party ISV access to our production environment. In case of abuse, we have the rights to revoke access untill problems have been resolved. Please send a mail to salesNO-SPAM@nedfox.nl to get access to our test environment. To go live at the end, it's required to have a fixed IP adress available.